Minor doc tweaks in use, preface, build. Try to segment Garmin list into

GPX and GPX-not.

diff --git a/xmldoc/chapters/build.xml b/xmldoc/chapters/build.xml
index 67284051c3436355ac56cb4f01806cc2131c68e5..377f8f9dcb24fb2758f7616a972ef91263030c5b 100644 (file)
--- a/xmldoc/chapters/build.xml
+++ b/xmldoc/chapters/build.xml
@@ -37,7 +37,7 @@ need to 'apt-get install libusb-dev'.
 </para>
 <para><userinput>./configure --help</userinput></para> 
 <para>
-lists all the supported options, but additionally we have:
+lists all the supported options, but additionally we have:</para><para>
  <option>--disable-shapefile</option> Excludes the shapefile support.
 </para>
 <para>

diff --git a/xmldoc/chapters/preface.xml b/xmldoc/chapters/preface.xml
index a839143e60dc096891e55b61ad649b5b29857e64..4ce0e356a1cb3b5ea8d95536c410572ac4f36541 100644 (file)
--- a/xmldoc/chapters/preface.xml
+++ b/xmldoc/chapters/preface.xml
@@ -1,7 +1,7 @@
    <preface id="Introduction">
       <title>Introduction</title>
       <section id="The_Problem">
-         <title>The Problem: Too many incompatible formats</title>
+         <title>The Problem: Too many incompatible GPS file formats</title>
          <para> There are simply too many gratuitously different file formats
 to hold waypoint, track, and route information in various programs
 used by computers and GPS receivers.  

diff --git a/xmldoc/chapters/use.xml b/xmldoc/chapters/use.xml
index 42bb089889f447e805eb82134983b0a27cca01cc..167f475b386f8943c67c7f54f20adbef9a36fa5b 100644 (file)
--- a/xmldoc/chapters/use.xml
+++ b/xmldoc/chapters/use.xml
@@ -54,15 +54,15 @@ name of a file to be read or written.
          it from, what you're writing, and what to write it to.  For
          example:</para>
          <para><userinput>gpsbabel -i geo -f /tmp/geocaching.loc -o gpx -F /tmp/geocaching.gpx</userinput></para>
-         <para>tells it to read the file "/tmp/geocaching.loc" in geocaching.com
-         format and create a new file in GPX format.</para>
+         <para>tells it to read the file <filename>/tmp/geocaching.loc</filename> in geocaching.com
+         format and create a new file <filename>/tmp/geocaching.gpx</filename> in GPX format.   It's important to note that the names have nothign to do with the formats actually used.</para>
          <para> This command will read from a Magellan unit attached
          to the first serial port on a Linux system (device names will
-         vary on other OSes) and write them as a geocaching loc file.
-         The second command does the same on Microsoft Windows.</para>
+         vary on other OSes) and write them as a geocaching loc file.</para>
          <para><userinput>gpsbabel -i magellan -f /dev/ttyS0 -o geo -F mag.loc</userinput></para>
+         <para>This second command does the same on Microsoft Windows.</para>
          <para><userinput>gpsbabel -i magellan -f com1 -o geo -F mag.loc</userinput></para>
-         <para>Optionally, you may specify <parameter moreinfo="none">"-s"</parameter> in any command line.  This
+         <para>Optionally, you may specify <parameter moreinfo="none">-s</parameter> in any command line.  This
          causes the program to ignore any "short" names that may be
          present in the source data format and synthesize one from the
          long name.  This is particularly useful if you're writing to
@@ -81,7 +81,7 @@ name of a file to be read or written.
        <para>
          Many of the available format options in GPSBabel can themselves
          take options.   While we try to make all the formats do the most
-         sensible thing possible without any extra options, this allows
+         sensible thing possible without any extra options; this allows
          great power and flexibility in the operation of the program.
        </para>
        <para>
@@ -136,7 +136,7 @@ merged data to multiple destinations.
          of supported character sets with "gpsbabel -l".  To change
          the character set on both sides you should do this:</para>
          <para><userinput>gpsbabel -i xcsv,style=foo.style -c latin1 -f foo -o xcsv,style=bar.style -c ms-ansi -F bar</userinput></para>
-         <para>Note, that some formats has a fixed character set and ignore this option.</para>
+         <para>Note, that some formats have a fixed character set and ignore this option.</para>
       </sect1>
       <sect1 id="Route_And_Track_Modes">
          <title>Route and Track Modes</title>
@@ -162,7 +162,7 @@ merged data to multiple destinations.
         may not really be the route you had in mind.
         </para>
          <para> Tracks and routes will sometimes be converted to a
-         list of waypoints when necessary, f.i. when writing into one
+         list of waypoints when necessary, One example is when writing into one
          of the CSV formats. The inverse operation is not supported
          right now, so reading the converted track back from CSV will
          always result in a list of waypoints, not the original track.

diff --git a/xmldoc/formats/garmin.xml b/xmldoc/formats/garmin.xml
index 3f30e6a93612b784c848af6ec42193576bfce26c..3a0c74de31e0842a9161ae64a732eb28910194b8 100644 (file)
--- a/xmldoc/formats/garmin.xml
+++ b/xmldoc/formats/garmin.xml
@@ -50,21 +50,6 @@
 <member>GPSMAP 76Cx</member> 
 <member>GPSMAP 96</member> 
 <member>GPSMAP 96C</member> 
-<member>Nuvi 300<footnote id="gpx"><para>This unit uses GPX format, not Garmin protocol.  Therefore one should communicate with it by reading and writing GPX files instead of using this format.  Members of this class of products do not support realtime positioning protocol.</para></footnote></member>
-<member>Nuvi 200<footnoteref linkend="gpx"/></member>
-<member>Nuvi 200W<footnoteref linkend="gpx"/></member>
-<member>Nuvi 250<footnoteref linkend="gpx"/></member>
-<member>Nuvi 250W<footnoteref linkend="gpx"/></member>
-<member>Nuvi 270<footnoteref linkend="gpx"/></member>
-<member>Nuvi 310<footnoteref linkend="gpx"/></member>
-<member>Nuvi 350<footnoteref linkend="gpx"/></member>
-<member>Nuvi 370<footnoteref linkend="gpx"/></member>
-<member>Nuvi 600<footnoteref linkend="gpx"/></member>
-<member>Nuvi 650<footnoteref linkend="gpx"/></member>
-<member>Nuvi 650FM<footnoteref linkend="gpx"/></member>
-<member>Nuvi 660<footnoteref linkend="gpx"/></member>
-<member>Nuvi 670<footnoteref linkend="gpx"/></member>
-<member>Nuvi 680<footnoteref linkend="gpx"/></member>
 <member>Quest</member>
 <member>Quest II</member>
 <member>Rhino 520</member>
@@ -83,15 +68,9 @@
 <member>StreetPilot c320</member>
 <member>StreetPilot c330</member>
 <member>StreetPilot c340</member>
-<member>StreetPilot c510<footnoteref linkend="gpx"/></member>
-<member>StreetPilot c530<footnoteref linkend="gpx"/></member>
-<member>StreetPilot c550<footnoteref linkend="gpx"/></member>
-<member>StreetPilot c580<footnoteref linkend="gpx"/></member>
 <member>StreetPilot i2</member>
 <member>StreetPilot i3</member>
 <member>StreetPilot i5</member>
-<member>Zumo 450<footnoteref linkend="gpx"/></member>
-<member>Zumo 550<footnoteref linkend="gpx"/></member>
 </simplelist>
 </para>
 <para>the following Bluetooth Garmin products:
@@ -100,6 +79,7 @@
 </simplelist>
 </para>
 
+
 <para>and most serial Garmin GPS receivers including:
 <simplelist columns="4">
 <member>eMap</member>
@@ -131,6 +111,36 @@
 </simplelist>
 </para>
 
+<para>
+The following Garmin GPS receivers are supported, but they do not
+support Garmin communication protocol and don't work with the 
+<option>garmin</option> option.  To use these receivers, read or write
+GPX files from the mass storage device as mounted on your computer.
+<simplelist columns="4">
+<member>Nuvi 200<footnoteref linkend="gpx"/></member>
+<member>Nuvi 200W<footnoteref linkend="gpx"/></member>
+<member>Nuvi 250<footnoteref linkend="gpx"/></member>
+<member>Nuvi 250W<footnoteref linkend="gpx"/></member>
+<member>Nuvi 270<footnoteref linkend="gpx"/></member>
+<member>Nuvi 300<footnote id="gpx"><para>This unit uses GPX format, not Garmin protocol.  Therefore one should communicate with it by reading and writing GPX files instead of using this format.  Members of this class of products do not support realtime positioning protocol.</para></footnote></member>
+<member>Nuvi 310<footnoteref linkend="gpx"/></member>
+<member>Nuvi 350<footnoteref linkend="gpx"/></member>
+<member>Nuvi 370<footnoteref linkend="gpx"/></member>
+<member>Nuvi 600<footnoteref linkend="gpx"/></member>
+<member>Nuvi 650<footnoteref linkend="gpx"/></member>
+<member>Nuvi 650FM<footnoteref linkend="gpx"/></member>
+<member>Nuvi 660<footnoteref linkend="gpx"/></member>
+<member>Nuvi 670<footnoteref linkend="gpx"/></member>
+<member>Nuvi 680<footnoteref linkend="gpx"/></member>
+<member>StreetPilot c510<footnoteref linkend="gpx"/></member>
+<member>StreetPilot c530<footnoteref linkend="gpx"/></member>
+<member>StreetPilot c550<footnoteref linkend="gpx"/></member>
+<member>StreetPilot c580<footnoteref linkend="gpx"/></member>
+<member>Zumo 450<footnoteref linkend="gpx"/></member>
+<member>Zumo 550<footnoteref linkend="gpx"/></member>
+</simplelist>
+</para>
+
 <para>
        None of the GPSBabel developers has access to every model on that
        list, but we've received reports of success and/or have reasonable